Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0893

reference: 262-tree-1
name: 0893
tree-preservation-order: undefined
262-tpo-1
uprn
address-text
point: POINT (-0.944164 50.858929)
geometry: MULTIPOLYGON (((-0.944108 50.858923,-0.944110 50.858934,-0.944118 50.858944,-0.944130 50.858952,-0.944146 50.858957,-0.944164 50.858959,-0.944181 50.858957,-0.944197 50.858953,-0.944210 50.858945,-0.944218 50.858935,-0.944221 50.858924,-0.944219 50.858912,-0.944211 50.858902,-0.944198 50.858894,-0.944183 50.858889,-0.944165 50.858887,-0.944148 50.858889,-0.944132 50.858894,-0.944119 50.858902,-0.944111 50.858912,-0.944108 50.858923)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL